feat: /a11y — accessibility testing built on the infrastructure you already have#152
Open
HMAKT99 wants to merge 3 commits intogarrytan:mainfrom
Open
feat: /a11y — accessibility testing built on the infrastructure you already have#152HMAKT99 wants to merge 3 commits intogarrytan:mainfrom
HMAKT99 wants to merge 3 commits intogarrytan:mainfrom
Conversation
…wse daemon Catches the death-by-a-thousand-cuts performance decay: - Before/after comparison using browse daemon's perf command - Core Web Vitals tracking (TTFB, FCP, LCP, DOM Complete) - JS/CSS bundle size monitoring with regression thresholds - Resource waterfall analysis with optimization recommendations - Performance budget checking against industry standards - Trend analysis from historical benchmark data - Diff-aware mode: only benchmark pages affected by current branch
Accessibility compliance testing that leverages gstack's accessibility tree: - WCAG 2.2 Level A/AA/AAA audits against real pages - Heading hierarchy, landmark, and document structure validation - Color contrast ratio calculation with specific fix suggestions - Keyboard navigation testing via Tab traversal - ARIA validation from the snapshot accessibility tree - Form label and image alt text verification - Mobile accessibility at responsive viewpoints - Compliance scoring with per-criterion pass/fail
HMAKT99
changed the title
Per maintainer feedback: generated .md files should not be committed. Only the .tmpl template is source of truth. Build generates the .md.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The accessibility tree was there all along
Every time you run
$B snapshot -i, gstack callspage.accessibility.snapshot()and reads the full ARIA tree. It assigns @e refs from it. The entire ref system — the thing that makes gstack's browser work — is built on the accessibility tree.But nobody is using it to actually test accessibility.
/a11ychanges that. It takes the accessibility tree gstack already reads and runs a WCAG 2.2 compliance audit against it. Same$Bcommands. Same browse daemon. New superpower.What it looks like
Why this belongs in gstack
It uses what you already built
$B snapshot$B snapshot -i$B snapshot -C$B eval$B press Tab$B viewportIt follows gstack's existing patterns
/a11y --diffonly audits pages affected by current branch — same pattern as/qa/reviewalt='Team photo of 5 engineers at the YC office'toimg.team-photo" — same specificity as/reviewThe world needs it now
Audit methodology
Arguments
Test plan
bun test— all tests pass, 0 failuresbun run gen:skill-docs --dry-run— FRESH{{PREAMBLE}}+{{BROWSE_SETUP}}— follows template pipeline.gstack/a11y-reports/